System and method for running a validation process for an information handling system during a factory process

ABSTRACT

An information handling system includes a memory and a processor. The memory to store a script and an exemption list for a validation process, and the script and the exemption list are received from a server. The processor is in communication with the memory, and configured to send a validation process pass indicator in response to a validation process error file being empty; in response to the validation process error file not being empty: to read a line of the validation process error file, to determine whether an error on the line of the validation process error file is found in an exemption list, and to add the error to an error log in response the error not being found in the exemption list; and to send the validation process pass indication in response to the error log being empty, otherwise sending a validation process fail indication.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. patent application Ser. No.14/219,308, entitled “System and Method for Running a Validation Processfor an Information Handling System During a Factory Process,” filed onMar. 19, 2014, the disclosure of which is hereby expressly incorporatedby reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure generally relates to running validation processfor an information handling system during a factory process.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, or communicatesinformation or data for business, personal, or other purposes.Technology and information handling needs and requirements can varybetween different applications. Thus information handling systems canalso vary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information can be processed, stored, orcommunicated. The variations in information handling systems allowinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing, airlinereservations, enterprise data storage, or global communications. Inaddition, information handling systems can include a variety of hardwareand software resources that can be configured to process, store, andcommunicate information and can include one or more computer systems,graphics interface systems, data storage systems, networking systems,and mobile communication systems. Information handling systems can alsoimplement various virtualized architectures. Data and voicecommunications among information handling systems may be via networksthat are wired, wireless, or some combination.

During a manufacturing/factory process of an information handlingsystem, different drivers/software are installed for hardware componentsof the information handling system. Checks can be performed to ensurethat the drivers/software are compliant with requirements made by themanufacturer.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures are not necessarily drawn to scale.For example, the dimensions of some elements may be exaggerated relativeto other elements. Embodiments incorporating teachings of the presentdisclosure are shown and described with respect to the drawings herein,in which:

FIG. 1 is a block diagram of a system during a factory process for aninformation handling system;

FIG. 2 is a flow diagram of a method for generating a script portion ofa validation process;

FIG. 3 is a flow diagram of a method for executing a validation processduring a factory process of the information handling system; and

FIG. 4 is a block diagram illustrating an information handling systemaccording, to an embodiment of the present disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF THE DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The descriptionis focused on specific implementations and embodiments of the teachings,and is provided to assist in describing the teachings. This focus shouldnot be interpreted as a limitation on the scope or applicability of theteachings.

FIG. 1 shows a system 100 during a factory process for an informationhandling system 102. For purposes of this disclosure, an informationhandling system can include any instrumentality or aggregate ofinstrumentalities operable to compute, calculate, determine, classify,process, transmit, receive, retrieve, originate, switch, store, display,communicate, manifest, detect, record, reproduce, handle, or utilize anyform of information, intelligence, or data for business, scientific,control, or other purposes. For example, an information handling systemmay be a personal computer (e.g., desktop or laptop), tablet computer,mobile device (e.g., personal digital assistant (PDA) or smart phone),server (e.g., blade server or rack server), a network storage device, orany other suitable device and may vary in size, shape, performance,functionality, and price. The information handling system may includerandom access memory (RAM), one or more processing resources such as acentral processing unit (CPU) or hardware or software control logic,ROM, and/or other types of nonvolatile memory. Additional components ofthe information handling system may include one or more disk drives, oneor more network ports for communicating with external devices as well asvarious input and output (I/O) devices, such as a keyboard, a mouse,touchscreen and/or a video display. The information handling system mayalso include one or more buses operable to transmit communicationsbetween the various hardware components.

FIG. 1 is an illustration of a system 100 including an informationhandling system 102 and a factory server 104. The information handlingsystem 102 is in communication with the factory server 104 via a network106. The factory server 104 includes stored thereon a script 112 to beexecuted during a validation process for applications and drivers to bepreinstalled on build-to-order (“BTO”) computer systems, represented inFIG. 1 by a information handling system 102. The information handlingsystem 102 includes a processor 108 and a hard disk driver 100. Thefactory server 104 also includes an exemption list 114 to be utilizedduring the validation process. The factory server 104 can also includefactory installation packages, which can be utilized by the informationhandling system 102 to installation hardware and associated driversduring a factory-installation stage of the manufacturing process. Indifferent embodiments, the script 112, the exemption list 114, and thefactory installation packages can be stored in a common memory orseparates memories of the factory server 104.

During the factory-installation stage, responsive to a command from theinformation handling system 102 to the factory server 104 to downloadone of the factory installation packages, the factory-install package isdownloaded from the server to the information handling system onto whichthe application or driver is to be preinstalled.

In particular, a “PARTS” file for the information handling system 102includes a list of part numbers corresponding to selected installationpackages for applications and drivers to be installed thereon. Theselected packages are downloaded over the network 106 to the hard disk110, and the applications and drivers installed on the informationhandling system 102 in the order in which they are listed in the PARTSfile. Also, during the factory-installation, the processor 108 canperform a validation check on the installed drivers, via scriptingengine of the processor executing the script 112 as described below. Inan embodiment, the validation check/process can be a CHKLOGO tool thatcan be executed using a scripting language, such as Python or the like,in an operating system, such as WinPE or the like, of the processor 108.

During the factory-installation, the factory server 104 can configurethe script 114 for the validation process. While configuring the script114, the factory server 104 can determine whether any skip conditionsexist for the validation process. In an embodiment, the skip conditionscan be different conditions that are based on a development level of theinformation handling system, based on bypass flags, or on the line ofbusiness for the information handling system. For example, thedevelopment level of an information handling system can be that theinformation handling system is at the prototype level, such that thevalidation process should be skipped because the low level of productionfor the information handling system 102 can cause the validation processto fail for the information handling system.

In an embodiment the bypass flag can be associated with a part installedin the information handling system 102. For example, a particularpart/component can be identified as a component not to test because thepart has test signed drivers assign to it at this developmental phase ofthe information handling system 102, and the test signed drivers cancause the validation process to fail. However, these signed test driverscan be replaced with properly authenticated drivers later in the factoryprocess, and then a different check process can be used to verify thedrivers. In an embodiment, the line of business skip condition can beassociated with a particular product line that does not need to complywith specific standards. For example, the manufacturer may have multipleproduct lines and one or more of the lines may not be required to havespecific drivers/software for components in the information handlingsystem 102 based on an agreement with the manufacturer of the componentand/or driver/software.

If the factory server 104 determines skip conditions for the validationprocess, the factory server 104 may not provide the script 112 to theinformation handling system, such that the validation process cannot beperformed by the processor 108. However, if factory server 104determines that no skip conditions exist, the factory server can sendthe validation process script 112, the exemption list 114, data files,and tools to the information handling system 102 to be stored in thehard disk 110. When the script 112 and exemption list 114 are stored inthe hard disk 110, the scripting engine of the processor 108 may make afew more modifications to the script 112. In particular, the processor108 can determine whether non-fail conditions exist for the driversinstalled on the information handling system 102. In an embodiment, thenon-fail conditions can be similar to this skip conditions, such asdevelopment level conditions. Non-fail conditions can also includeinstructions to run the validation process, but any fail conditions thatare detected are ignored (run but do not fail conditions). In anembodiment, the run but do not fail conditions can be specificconditions that can cause the validation process to be executed andfailures to be logged without ending the validation process for thatparticular machine. For example, without these non-fail conditions, anydetected error will result in a notification that the informationhandling system has failed and needs to be re-tested and reconfigured.However, if the detected error matches one of the run but do not failconditions, the failure notification will not be provided to a user.

If any non-fail conditions exist, the processor 108 can modify thescript 112 to include the non-failure conditions. The processor 108 canthen insert a command to cause the validation process to be executedwhen the operating system of the information handling system is online.

When the scripting engine of the processor 108 begins executing thevalidation process, a model number of the information handling system102. The processor 108 then retrieves the exemption list from the harddisk 110. In an embodiment, the exemptions can include items that willbe checked by other processes later in the main factory process, drivermanufacture exemptions, test signed drivers, and the like. The drivermanufacture exemptions can be for components that a manufacturer hasindicated that the component or components can be installed in theinformation handling system 102 without the associated driver beingchecked. In an embodiment, the test signed drivers are drivers that aresigned (authenticated) early in the factory process to so that thedrivers appear authenticated to the operating system of the informationhandling system but that would cause a failure during the validationprocess. These signed test drivers can be exempt from creating an errorbecause they will be corrected at the end of the factory process.

A validation process error file is created during the execution of thevalidation process. The processor 108 can determine whether thevalidation process error file is empty. If the error file is empty, theprocessor 108 sends a validation process pass indication, and ends thevalidation process. In an embodiment, the validation process passindication can be a visual indicator to a user, such as lighting ascreen a particular color. However, if the error file is not empty, theprocessor 108 reads a line of the error file and determines whether theerror and the associated model number found in the line of the errorfile match an entry in the exemption list 114. If the error and modelnumber are not found in the exemption list, the processor 108 adds theerror to an error log.

However, if the error and model number are found in the exemption list,the processor determines whether the error is handled at another portionof the factory process. If not, the processor 108 adds the error to anerror log. The processor 108 then continues these operations until theprocessor has evaluated every line of the error file. The processor 108then determines whether the error log is empty. If the error file isempty, the processor 108 sends the validation process pass indication.However, if the validation error log is not empty, the processor sends avalidation process fail indication. In an embodiment, the validationprocess fail indication can be a visual indicator to a user, such aslighting a screen a particular color that is different from the color ofthe validation process pass indication.

FIG. 2 shows a method of a flow diagram of a method 200 for generating ascript portion of a validation process. At block 202, a validationscript configuration process begins. In an embodiment, the validationscript configuration process can be used in a validation process, whichcan be a tool to verify that different components/hardware installedwithin information handling system during a manufacturing process haveproper drivers/software installed that are compliant with standards setby the manufacturers of the drivers/software. A determination is madewhether any skip conditions exist for the validation process at block204. In an embodiment, the skip conditions can be different conditionsthat are based on a development level of the information handlingsystem, based on bypass flags, or on the line of business for theinformation handling system. The development level of an informationhandling system can be that the information handling system is at theprototype level, which can be the lowest level of production. In anembodiment the bypass flag can be associated with a part installed inthe information handling system. For example, a particularpart/component can be identified as a component not to test because thepart has test signed drivers assign to it at this developmental phase,and the test signed drivers can cause the validation process to fail.However, these signed test drivers can be replaced with properlyauthenticated drivers later in the factory process, and then a differentcheck process can be used to verify the drivers at that time. In anembodiment, the line of business skip condition can be associated with aparticular product line that does not need to comply with specificstandards. For example, the manufacturer may have multiple product linesand one or more of the lines may not be required to have specificdrivers/software for components in the information handling system basedon an agreement with the manufacturer of the component and/ordriver/software.

If no skip conditions exist, validation process script, data files, andtools are received from the server at block 206, otherwise thevalidation script configuration process ends at block 214. At block 208,a determination is made whether non-fail conditions exist. In anembodiment, the non-fail conditions can be similar to this skipconditions, such as development level conditions. Non-fail conditionscan also include instructions to run the validation process, but anyfail conditions that are detected are ignored (run but do not failconditions). In an embodiment, the run but do not fail conditions can bespecific conditions that can cause the validation process to be executedand log failures without ending the validation process for thatparticular machine. For example, without these non-fail conditions, anydetected error will result in a notification that the informationhandling system has failed and needs to be re-tested and reconfigured.However, the run but do not fail conditions can prevent the failurenotification from being provided to a user.

If any non-fail conditions exist, the validation process script ismodified to include the non-failure conditions at block 210. At block212, a command to execute the validation process when the operatingsystem of the information handling system is online is inserted into thevalidation process, and the validation script configuration process isended at block 214.

FIG. 3 shows a flow diagram of a method 300 for executing a validationprocess during a factory process of the information handling system. Atblock 302, the validation process is begun. A model number of thecurrent information handling system is retrieved at block 304. In anembodiment, the model name can be provided in a standard format to beaccessed by the validation process. At block 306, the validation processtool is executed. An exemption list is retrieved at block 308. In anembodiment, the exemption list can be retrieved from a server within thefactory process for the information handling system, and the exemptionscan be errors that will not cause the validation process for the currentinformation handling system to fail. In an embodiment, the exemptionscan include items that will be checked by other processes later in themain factory process, driver manufacture exemptions, test signeddrivers, and the like. The driver manufacture exemptions can be forcomponents that a manufacturer has indicated that the component orcomponents can be put in the information handling system without theassociated driver being checked. In an embodiment, the test signeddrivers are drivers that are signed (authenticated) early in the factoryprocess to so that the drivers appear authenticated to the operatingsystem of the information handling system but that would cause a failureduring the validation process. These signed test drivers can be exemptfrom creating an error because they will be corrected at the end of thefactory process.

A determination of whether the validation process error file is empty ismade at block 310. If the error file is empty, a validation process passis reported at block 312, and the validation process ends at block 314.However, if the error file is not empty, a line of the error file isread at block 316. At block 318, a determination is made whether theerror and the associated model number match an entry in the exemptionlist. If the error and model number are not found in the exemption list,the error is added to an error log at block 320.

At block 322, a determination is made whether the error is handled atanother portion of the factory process. If the error is not handled atanother part of the factory process, the flow continues at block 320 asdescribed above. However, if the error is handled at another part of thefactory process, a determination is made whether the error file iscompletely processed at block 324.

If the error file is not completely processed, the flow continues asstated above at block 316. If the error file is completely processed, adetermination is made whether the error log is empty at block 326. Ifthe error file is empty, a validation pass indication is reported atblock 312, and the validation process and at block 314. However, if thevalidation error log is not empty, the validation process failindication is reported at block 328, and the validation process ends atblock 314.

FIG. 4 shows an information handling system 400 capable of administeringeach of the specific embodiments of the present disclosure. Theinformation handling system 400 can represent the information handlingsystem 102, the server 104, or other system located anywhere withinnetwork 100 of FIG. 1, including the remote data center or cloud 180operating the virtual machine applications described herein. Theinformation handling system 400 may include a processor 402 such as acentral processing unit (CPU), a graphics processing unit (GPU), orboth. Moreover, the information handling system 400 can include a mainmemory 404 and a static memory 407 that can communicate with each othervia a bus 408. The information handling system 400 includes near-fieldcommunications (NFC) device and interface 418, such as an antenna andNFC subsystem. The information handling system 400 can also include adisk drive unit 416, and a network interface device 420. As shown, theinformation handling system 400 may further include a video display unit410, such as a liquid crystal display (LCD), an organic light emittingdiode (OLED), a flat panel display, a solid state display, or a cathoderay tube (CRT). The video display unit 410 may also act as an inputaccepting touchscreen inputs. Additionally, the information handlingsystem 400 may include an input device 412, such as a keyboard, or acursor control device, such as a mouse or touch pad. Informationhandling system may include a battery system 414. The informationhandling system 400 can represent a device capable of telecommunicationsand whose can be share resources, voice communications, and datacommunications among multiple devices. The information handling system400 can also represent a server device whose resources can be shared bymultiple client devices, or it can represent an individual clientdevice, such as a laptop or tablet personal computer.

The information handling system 400 can include a set of instructionsthat can be executed to cause the computer system to perform any one ormore of the methods or computer based functions disclosed herein. Thecomputer system 400 may operate as a standalone device or may beconnected such as using a network, to other computer systems orperipheral devices.

In a networked deployment, the information handling system 400 mayoperate in the capacity of a server or as a client user computer in aserver-client user network environment, or as a peer computer system ina peer-to-peer (or distributed) network environment. The informationhandling system 400 can also be implemented as or incorporated intovarious devices, such as a personal computer (PC), a tablet PC, aset-top box (STB), a smartphone, a PDA, a mobile device, a palmtopcomputer, a laptop computer, a desktop computer, a communicationsdevice, a wireless telephone, a land-line telephone, a control system, acamera, a scanner, a facsimile machine, a printer, a pager, a personaltrusted device, a web appliance, a network router, switch or bridge, orany other machine capable of executing a set of instructions (sequentialor otherwise) that specify actions to be taken by that machine. In aparticular embodiment, the computer system 400 can be implemented usingelectronic devices that provide voice, video or data communication.Further, while a single information handling system 400 is illustrated,the term “system” shall also be taken to include any collection ofsystems or subsystems that individually or jointly execute a set, ormultiple sets, of instructions to perform one or more computerfunctions.

The disk drive unit 416 or static memory 414 may include acomputer-readable medium 422 in which one or more sets of instructions424 such as software can be embedded. The disk drive unit 416 or staticmemory 414 also contains space for data storage. Further, theinstructions 424 may embody one or more of the methods or logic asdescribed herein. In a particular embodiment, the instructions 424 mayreside completely, or at least partially, within the main memory 404,the static memory 406, and/or within the processor 402 during executionby the information handling system 400. The main memory 404 and theprocessor 402 also may include computer-readable media. The networkinterface device 420 can provide connectivity to a network 426, e.g., awide area network (WAN), a local area network (LAN), wireless network(IEEE 802), or other network. The network interface 420 may alsointerface with macrocellular networks including wirelesstelecommunications networks such as those characterized as 2G, 3G, or 4Gor similar wireless telecommunications networks similar to thosedescribed above. The network interface 420 may be a wireless adapterhaving antenna systems 432 for various wireless connectivity and radiofrequency subsystems 430 for signal reception, transmission, or relatedprocessing.

In an alternative embodiment, dedicated hardware implementations such asapplication specific integrated circuits, programmable logic arrays andother hardware devices can be constructed to implement one or more ofthe methods described herein. Applications that may include theapparatus and systems of various embodiments can broadly include avariety of electronic and computer systems. One or more embodimentsdescribed herein may implement functions using two or more specificinterconnected hardware modules or devices with related control and datasignals that can be communicated between and through the modules, or asportions of an application-specific integrated circuit. Accordingly, thepresent system encompasses software, firmware, and hardwareimplementations. In accordance with various embodiments of the presentdisclosure, the methods described herein may be implemented by softwareprograms executable by a computer system. Further, in an exemplary,non-limited embodiment, implementations can include distributedprocessing, component/object distributed processing, and parallelprocessing. Alternatively, virtual computer system processing can beconstructed to implement one or more of the methods or functionality asdescribed herein.

The present disclosure contemplates a computer-readable medium thatincludes instructions 424 or receives and executes instructions 424responsive to a propagated signal; so that a device connected to anetwork 428 can communicate voice, video or data over the network 428.Further, the instructions 424 may be transmitted or received over thenetwork 428 via the network interface device 420. In a particularembodiment, BIOS/FW code 424 reside in memory 404, and includemachine-executable code that is executed by processor 402 to performvarious functions of information handling system 400.

Information handling system 400 includes one or more applicationprograms 424, and Basic Input/Output System and Firmware (BIOS/FW) code424. BIOS/FW code 424 functions to initialize information handlingsystem 400 on power up, to launch an operating system, and to manageinput and output interactions between the operating system and the otherelements of information handling system 400.

In another embodiment (not illustrated), application programs andBIOS/FW code reside in another storage medium of information handlingsystem 400. For example, application programs and BIOS/FW code canreside in drive 416, in a ROM (not illustrated) associated withinformation handling system 400, in an option-ROM (not illustrated)associated with various devices of information handling system 400, instorage system 407, in a storage system (not illustrated) associatedwith network channel 420, in another storage medium of informationhandling system 400, or a combination thereof. Application programs 424and BIOS/FW code 424 can each be implemented as single programs, or asseparate programs carrying out the various features as described herein.

While the computer-readable medium is shown to be a single medium, theterm “computer-readable medium” includes a single medium or multiplemedia, such as a centralized or distributed database, and/or associatedcaches and servers that store one or more sets of instructions. The term“computer-readable medium” shall also include any medium that is capableof storing, encoding, or carrying a set of instructions for execution bya processor or that cause a computer system to perform any one or moreof the methods or operations disclosed herein.

In a particular non-limiting, exemplary embodiment, thecomputer-readable medium can include a solid-state memory such as amemory card or other package that houses one or more non-volatileread-only memories. Further, the computer-readable medium can be arandom access memory or other volatile re-writable memory. Additionally,the computer-readable medium can include a magneto-optical or opticalmedium, such as a disk or tapes or other storage device to storeinformation received via carrier wave signals such as a signalcommunicated over a transmission medium. Furthermore, a computerreadable medium can store information received from distributed networkresources such as from a cloud-based environment. A digital fileattachment to an e-mail or other self-contained information archive orset of archives may be considered a distribution medium that isequivalent to a tangible storage medium. Accordingly, the disclosure isconsidered to include any one or more of a computer-readable medium or adistribution medium and other equivalents and successor media, in whichdata or instructions may be stored.

In the embodiments described herein, an information handling systemincludes any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, oruse any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a consumerelectronic device, a network server or storage device, a switch router,wireless router, or other network communication device, a networkconnected device (cellular telephone, tablet device, etc.), or any othersuitable device, and can vary in size, shape, performance, price, andfunctionality.

The information handling system can include memory (volatile (e.g.random-access memory, etc.), nonvolatile (read-only memory, flash memoryetc.) or any combination thereof), one or more processing resources,such as a central processing unit (CPU), a graphics processing unit(GPU), hardware or software control logic, or any combination thereof.Additional components of the information handling system can include oneor more storage devices, one or more communications ports forcommunicating with external devices, as well as, various input andoutput (I/O) devices, such as a keyboard, a mouse, a video/graphicdisplay, or any combination thereof. The information handling system canalso include one or more buses operable to transmit communicationsbetween the various hardware components. Portions of an informationhandling system may themselves be considered information handlingsystems.

When referred to as a “device,” a “module,” or the like, the embodimentsdescribed herein can be configured as hardware. For example, a portionof an information handling system device may be hardware such as, forexample, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a stand-alone device).

The device or module can include software, including firmware embeddedat a device, such as a Pentium class or PowerPC™ brand processor, orother such device, or software capable of operating a relevantenvironment of the information handling system. The device or module canalso include a combination of the foregoing examples of hardware orsoftware. Note that an information handling system can include anintegrated circuit or a board-level product having portions thereof thatcan also be any combination of hardware and software.

Devices, modules, resources, or programs that are in communication withone another need not be in continuous communication with each other,unless expressly specified otherwise. In addition, devices, modules,resources, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

What is claimed is:
 1. An information handling system comprising: amemory to store a script and an exemption list for a validation process,wherein the script and the exemption list are received from a server;and a processor in communication with the memory, the processorconfigured to send a validation process pass indicator in response to avalidation process error file being empty; in response to the validationprocess error file not being empty: 1) to read a line of the validationprocess error file, 2) to determine whether an error on the line of thevalidation process error file is found in an exemption list, 3) to addthe error to an error log in response the error not being found in theexemption list, and 4) to determine whether the error is handled inanother portion of a manufacturing process, and in response to the errornot being handled in another portion of the manufacturing process, toadd the error to the error log.
 2. The information handling system ofclaim 1, wherein the validation process error file is created during anexecution of a validation process.
 3. The information handling system ofclaim 1, wherein the processor further to send the validation processpass indication in response to the error log being empty, otherwisesending a validation process fail indication.
 4. The informationhandling system of claim 1, wherein the processor further to retrieve amodel name of the information handling system, and to read an exemptionlist prior to determining whether the validation process error file isempty.
 5. The information handling system of claim 1, wherein thevalidation process pass indication is sent when a screen a first color.6. The information handling system of claim 5, wherein the validationprocess fail indication is sent when the screen is lit a second colordifferent than the first color.
 7. A method comprising: determining, bya processor, whether a validation process error file is empty; inresponse to the validation process error file being empty, sending avalidation process pass indicator; in response to the validation processerror file not being empty: reading, by the processor, a line of thevalidation process error file; determining, by the processor, whether anerror on the line of the validation process error file and a modelnumber of an information handling system are found in an exemption listfor a validation process during a manufacturing process of theinformation handling system; in response to the error and the modelnumber being found in the exemption list determining, by the processor,whether the error is handled in another portion of the manufacturingprocess of the information handling system; in response to the error notbeing handled in another portion of the manufacturing process, addingthe error to an error log; and in response to the error file beingcompletely processed, determining whether the error log is empty.
 8. Themethod of claim 7, further comprising: in response to the error logbeing empty, sending the validation process pass indication, otherwisesending a validation process fail indication.
 9. The method of claim 7,wherein the validation process error file is created during an executionof a validation process.
 10. The method of claim 7, further comprising:retrieving a model name of the information handling system; and readingan exemption list prior to determining whether the validation processerror file is empty.
 11. The method of claim 7, wherein sending thevalidation process pass indication comprises: lighting a screen a firstcolor.
 12. The method of claim 11, wherein sending the validationprocess fail indication comprises: lighting the screen a second colordifferent than the first color.
 13. A method comprising: determining, ata server, whether skip conditions exist for a validation process of aninformation handling system; in response to skip conditions not existingfor the validation process: sending a script and an exemption list forthe validation process from the server to the information handlingsystem; and determining whether a validation process error file isempty; in response to the validation process error file not being empty:reading, by the processor, a line of the validation process error file;determining, by the processor, whether an error on the line of thevalidation process error file and a model number of an informationhandling system are found in an exemption list for a validation processduring a manufacturing process of the information handling system; inresponse the error and the model number being found in the exemptionlist, determining whether the error is handled in another portion of themanufacturing process of the information handling system; in response tothe error not being handled in another portion of the manufacturingprocess the error to an error log; and in response to the error filebeing completely processed, determining whether the error log is empty;and in response to the error log being empty, sending the validationprocess pass indication, otherwise sending a validation process failindication.
 14. The method of claim 13, wherein the script and theexemption list are not sent in response to skip conditions existing. 15.The method of claim 13, wherein the validation process error file iscreated during an execution of the validation process.
 16. The method ofclaim 13, further comprising: retrieving a model name of the informationhandling system; and reading an exemption list prior to determiningwhether the validation process error file is empty.
 17. The method ofclaim 13, wherein sending the validation process pass indicationcomprises: lighting a screen a first color.
 18. The method of claim 17,wherein sending the validation process fail indication comprises:lighting the screen a second color different than the first color.